Add metrics for AutoUpdatingSolverTokenOwnerFinder
#842
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Sometimes the new token owner finder implementation is quite noisy because it always logs an error when something fails. However, those errors tend to be temporary, not critical and not really actionable (because we are relying on external servers).
To not let the alert channels become too noisy we can simply add a few metrics and alert based on those.
In order to have meaningful metrics we need to have some identifier associated with them (in case we have to query more urls in the future). To not introduce unnecessary complexity I decided to simply use the urls as the identifier.
Test Plan
Manual test running the order book locally and grepping for the new metrics: